Repository navigation
fix: сортировка участников по активности и пустым датам - #812
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Participants now default to most recently active first. In the inactive-first order, missing activity dates come first, followed by oldest activity; equal dates remain stable by profile ID. List, filtered selection and Excel use the same order. Explicit registration ordering remains compatible.
No schema, data or permission changes. Validation: 40 PostgreSQL participant, management and bulk regression tests passed; changed Python files pass Black and diff checks. Includes default ordering, NULL placement, stable pagination/ties, filters, selection, typed Excel and existing permission cases.